Publication: AppForge v1.0.0 — rename, badges, canonical status doc - #9
Merged
Merged
Conversation
The project has been AppForge since the MCP engine rewrite, but the
package metadata, prompts, config comments, and UI still said
DevTeam.AI. Rename the product and package everywhere in active code,
and point the placeholder project URLs at the real repository.
- pyproject: name devteam-ai -> appforge, version 0.1.0 -> 1.0.0,
classifier Alpha -> Production/Stable, your-repo URLs -> adbarc92
- frontend: package version 0.0.0 -> 1.0.0, page title "frontend" ->
"AppForge" (backend/main.py already declared 1.0.0)
- prompts, config/*.yaml, agents, tests, CI, phase briefs: DevTeam.AI
-> AppForge; DEVTEAM_PHASE -> APPFORGE_PHASE
- uv.lock regenerated for the rename + version
docs/superpowers/{plans,specs} are left untouched: they are dated
design records that quote code verbatim, so rewriting them would
falsify history.
Declare the project complete for now at v1.0 and give it a single accurate entry point. - docs/STATUS.md: new canonical, living status doc (state summary + newest-first session log). Supersedes the dated Status-*.md snapshots, which still described the retired LangGraph orchestrator. - README: CI/version/tests/coverage/python/license badges; a Configuration table for the env vars read by backend/config.py; the CLI flag table for run.py; frontend test command; v1.0 framing. - README: rebuild the architecture diagram, whose box borders were 41/42/43 chars on different lines and whose worker stems did not line up. Entry point now shows the invocation that actually works (python -m backend.engine.run) rather than the appforge console script, which is declared but not installed. - CLAUDE.md: replace the stale "Active session pickup" block, which pointed new sessions at Status-2026_06_02.md and Phase 6 work that the engine rewrite made moot; flag the LangGraph-era sections as historical.
adbarc92
changed the title
This was referenced Jul 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publication prep (the original mission), now that the engine is complete. This PR now carries the full v1.0 release, not just the README rewrite.
Stacked on #8 (final engine PR) so the README describes the merged system. Merge order: #7 → #8 → this.
1. Evidence-based README + MIT LICENSE (original scope)
docs/runs/2026-07-24/).2. Rename DevTeam.AI → AppForge
The project has been AppForge since the engine rewrite, but the package metadata, prompts, config comments, and UI still said DevTeam.AI.
pyproject: namedevteam-ai→appforge, placeholderyour-repoURLs → the real repository, authors → AppForge Contributorsconfig/*.yaml, agents, tests, CI, phase briefs,frontend/src/App.tsxDEVTEAM_PHASE→APPFORGE_PHASE; page titlefrontend→AppForgeuv.lockregenerateddocs/superpowers/{plans,specs}are deliberately left untouched — they are dated design records that quote code verbatim, so rewriting them would falsify history.3. Version 1.0.0
pyproject0.1.0→1.0.0, classifier3 - Alpha→5 - Production/Stablefrontend/package.json0.0.0→1.0.0(backend/main.pyalready declared 1.0.0)v1.0.04. Status doc + README polish
docs/STATUS.md— new canonical, living status doc (state summary + newest-first session log). Supersedes the datedStatus-*.mdsnapshots, which still described the retired LangGraph orchestrator.backend/config.py, and a CLI flag table forrun.py— neither was documented.python -m backend.engine.run) instead of theappforgeconsole script, which is declared inpyprojectbut not installed (the project has no[build-system]).CLAUDE.md— replaced the stale "Active session pickup" block, which pointed new sessions atStatus-2026_06_02.mdand Phase 6 work that the engine rewrite made moot; LangGraph-era sections now flagged as historical.Verification
uv run pytest tests/cd frontend && npm testuv run ruff check backend/ tests/uv run black --check backend/ tests/cd frontend && npm run build#testsanchor validKnown follow-ups (not in this PR)
[project.scripts] appforgeis declared but never installed — the project has no[build-system], souv syncskips entry points. Either add one or drop the declaration.ENABLE_PHASE4is now dead config:backend/config.pyreads it andtests/unit/test_config.pytests its default, but nothing consumes it (same shape as theSQLITE_PATHconfig dropped in cde5ab7).pyprojectstill depends onlangchain*and listscrewaiin keywords/mypy overrides, left over from the retired orchestrator.